Summary

Currently, members annotated with @deprecated, @experimental/@beta, or @legacy in the webpack type definitions render stability information as a plain heading (e.g. ###### Deprecated) at the bottom of the member section. This PR adds Node.js-style stability blockquotes that appear at the top of the member — before parameters and return type — following the format used in Node.js docs.

Two files are changed:

• plugins/theme/helpers/index.mjs — adds a new stabilityBlockquote(comment) helper that inspects a TypeDoc Comment object and returns the appropriate blockquote string or null:

  • @deprecated → > Stability: 0 - Deprecated[: message]
  • @experimental / @beta → > Stability: 1 - Experimental
  • @legacy → > Stability: 3 - Legacy[: message]

• plugins/theme/partials/index.mjs — updates the signature() partial to prepend the stability blockquote before all other content, and passes showTags: false to ctx.partials.comment() to prevent TypeDoc from also rendering a duplicate ###### Deprecated heading.

Before:

#### Static method: `clearChunkGraphForChunk(chunk)`

* `chunk` {Chunk}
* Returns: {void}

###### Deprecated

After:

#### Static method: `clearChunkGraphForChunk(chunk)`

> Stability: 0 - Deprecated

* `chunk` {Chunk}
* Returns: {void}

Note: Members rendered via the accessor partial bypass signature() and are not covered by this change (6 cases).
Accessor-level @deprecated tags use a separate render path (accessor partial) that calls comment() directly. These 6 cases are not yet fixed. Requesting maintainer input on the preferred approach. This can be addressed in a follow-up.

What kind of change does this PR introduce?

feat

Did you add tests for your changes?

No. The project does not currently have a test suite for theme partials/helpers. The output was verified manually by regenerating docs with npm run generate-docs and inspecting the changed pages.

Does this PR introduce a breaking change?

No.

If relevant, what needs to be documented once your changes are merged or what have you already documented?

No documentation changes needed. The stability blockquote format is self-explanatory and consistent with Node.js conventions.

Use of AI

I used Claude to assist with drafting parts of the implementation. All code was reviewed and understood before committing. I have read the AI policy at https://github.com/webpack/governance/blob/main/AI_POLICY.md.